If VTU reader fails parsing file as XML, try with legacy reader #203
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tarcila
approved these changes
Jan 26, 2026
Collaborator
tarcila
left a comment
tarcila
left a comment
There was a problem hiding this comment.
LGTM, Thanks!
According to VTK doc, legacy files should be .vtk and newer XML based should be .vtu. Not sure when those would be expecting to be mixed. But no harm in doing that fallback, and it seems similar to what ParaView does when using reader autodetection.
Contributor
Author
|
Yes this is right, legacy files should have the ending |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.